docs: add Fern scaffolding and publish agent docs - #238
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdds Fern site configuration, versioned 1.2 and 1.3 documentation, CI validation, release publishing, and pull-request preview workflows that upload artifacts and maintain preview comments. ChangesFern documentation platform
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant PullRequest
participant PreviewBuild
participant PreviewArtifact
participant PreviewComment
participant FernCLI
participant FernAPI
PullRequest->>PreviewBuild: trigger on documentation changes
PreviewBuild->>PreviewArtifact: upload preview sources and metadata
PreviewComment->>PreviewArtifact: download fern-preview
PreviewComment->>FernCLI: generate documentation preview
FernCLI-->>PreviewComment: return preview URL
PreviewComment->>FernAPI: resolve changed files to page slugs
PreviewComment-->>PullRequest: create or update preview comment
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
e802207 to
ff14edb
Compare
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/fern-docs-preview-comment.yml:
- Around line 46-84: The preview job currently runs fork-controlled Fern sources
with DOCS_FERN_TOKEN. Update the workflow condition governing the preview steps,
including the `Generate preview URL` path, to require that the workflow run
originates from a same-repository pull request before downloading artifacts,
installing the CLI, or invoking Fern; otherwise skip the job. Do not expose the
token to fork-provided inputs.
In @.github/workflows/publish-fern-docs.yml:
- Around line 62-65: Update the URL parsing block in the publish workflow to
fail explicitly when the published URL cannot be extracted from
/tmp/fern-output.log, instead of suppressing the grep failure or silently
skipping the summary. Preserve the existing GITHUB_STEP_SUMMARY output when a
URL is found.
- Around line 27-30: Update the release-triggered publish job to check out only
the canonical docs branch, or gate execution so non-current-version releases
cannot publish. In the Fern URL parsing step, validate that a published link was
emitted and explicitly fail the step when none is found, rather than allowing
the publish job to succeed silently.
In `@docs/1.2/usage.md`:
- Around line 140-142: Add the text language identifier to the fenced output
block containing “Enrollment succeeded” in docs/1.2/usage.md (lines 140-142),
and to the project-structure fenced block in docs/1.3/development.md (lines
33-52).
- Line 111: Correct the fleetint enroll command in the usage documentation by
inserting a space between the endpoint URL and the --token option, so they are
passed as separate arguments.
- Line 272: Update the metrics curl example in the usage documentation to
request the documented component name accelerator-nvidia-dcgm-thermal instead of
accelerator-nvidia-temperature.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: e520f767-6bb3-4b53-83cf-d197bb61bfaf
📒 Files selected for processing (24)
.github/workflows/fern-docs-ci.yml.github/workflows/fern-docs-preview-build.yml.github/workflows/fern-docs-preview-comment.yml.github/workflows/publish-fern-docs.ymlREADME.mddocs/1.2/architecture.mddocs/1.2/configuration.mddocs/1.2/development.mddocs/1.2/install-deb.mddocs/1.2/install-helm.mddocs/1.2/install-rpm.mddocs/1.2/usage.mddocs/1.3/architecture.mddocs/1.3/configuration.mddocs/1.3/development.mddocs/1.3/install-deb.mddocs/1.3/install-helm.mddocs/1.3/install-rpm.mddocs/1.3/usage.mddocs/index-1.2.ymldocs/index-1.3.ymlfern/.gitignorefern/docs.ymlfern/fern.config.json
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/publish-fern-docs.yml:
- Around line 63-66: Update the shell setup in the workflow step that runs Fern
generation to use `set -euo pipefail` instead of only enabling pipefail,
ensuring a nonzero `fern generate` failure terminates the step before the URL
validation and success summary.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 54343506-ef9f-4909-bf9c-64a3108b3357
📒 Files selected for processing (3)
.github/workflows/fern-docs-preview-comment.yml.github/workflows/publish-fern-docs.ymldocs/1.2/usage.md
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/1.2/usage.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/publish-fern-docs.yml:
- Around line 44-47: Update the Checkout repository step in the release-publish
workflow to explicitly check out the canonical documentation branch or commit
instead of the release event ref. Preserve workflow_dispatch behavior as
appropriate, ensuring publishes always use the current fern/docs.yml rather than
potentially stale release-tag contents.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: ea9f3097-7cd5-42d7-952a-8f05de749f8d
📒 Files selected for processing (1)
.github/workflows/publish-fern-docs.yml
691f00b to
f155707
Compare
There was a problem hiding this comment.
Actionable comments posted: 9
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/fern-docs-ci.yml:
- Around line 105-106: Validate the .version value with the existing preview
workflow’s semver validation before installation, assign it to VERSION, and
install the exact package using the VERSION variable. Apply this change at
.github/workflows/fern-docs-ci.yml lines 105-106 and
.github/workflows/publish-fern-docs.yml lines 54-55.
In `@docs/1.2/configuration.md`:
- Around line 196-201: Update the Kubernetes verification commands in
docs/1.2/configuration.md lines 196-201 and docs/1.3/configuration.md lines
203-206 to use helm get values --all, ensuring both examples display chart
defaults and user overrides.
- Around line 104-107: Pin the Helm chart version in both installation examples:
update docs/1.2/configuration.md lines 104-107 to use --version 1.2.1, and
docs/1.3/configuration.md lines 109-114 to use --version 1.3.0, preserving the
existing command structure.
In `@docs/1.2/install-helm.md`:
- Around line 172-178: Update the DCGM troubleshooting commands near the
DCGM_URL environment check to use the configured $DCGM_URL for connectivity
testing instead of the hardcoded nvidia-dcgm.gpu-operator.svc:5555 endpoint.
Make the kubectl service lookup explicitly default-only or otherwise
configurable, preserving the documented custom env.DCGM_URL override behavior.
In `@docs/1.2/install-rpm.md`:
- Around line 80-84: Update the release link and package version placeholders in
the installation and update sections to target the documented 1.2 release line:
link to the v1.2.1 release and require a compatible 1.2.x RPM instead of using
the latest release or unconstrained VERSION.
In `@docs/1.2/usage.md`:
- Around line 304-313: The “Exposing the Agent for External Monitoring”
documentation uses an unsafe all-interfaces listener as the primary example.
Make 127.0.0.1:15133 the default example, retain a specific remote address only
with guidance to restrict access through a firewall or private network, and
document that remote scraping should use a TLS-authenticated reverse proxy
because the TCP API is unauthenticated plaintext HTTP.
In `@docs/1.3/configuration.md`:
- Around line 63-65: Update the configuration documentation around the
duration-valued environment variable descriptions to state that the table covers
both Fleet Intelligence settings and process-level environment tuning. Remove
MALLOC_ARENA_MAX from the telemetry exporter and runtime interval description,
and describe its glibc allocator behavior separately.
In `@docs/1.3/development.md`:
- Around line 33-52: Update the project-structure code fence in the
documentation to include the `text` language identifier after the opening
backticks, preserving the diagram contents unchanged.
In `@docs/1.3/install-helm.md`:
- Around line 36-44: Update the enrollment Secret creation instructions under
“Create enrollment secret” to avoid passing ENROLL_TOKEN via the kubectl command
line. Use a safer input mechanism that does not expose the token in process
arguments, while preserving the existing secret name, namespace, and token key
behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: d4c79c0e-08d1-415f-88ee-2db8b2831965
📒 Files selected for processing (24)
.github/workflows/fern-docs-ci.yml.github/workflows/fern-docs-preview-build.yml.github/workflows/fern-docs-preview-comment.yml.github/workflows/publish-fern-docs.ymlREADME.mddocs/1.2/architecture.mddocs/1.2/configuration.mddocs/1.2/development.mddocs/1.2/install-deb.mddocs/1.2/install-helm.mddocs/1.2/install-rpm.mddocs/1.2/usage.mddocs/1.3/architecture.mddocs/1.3/configuration.mddocs/1.3/development.mddocs/1.3/install-deb.mddocs/1.3/install-helm.mddocs/1.3/install-rpm.mddocs/1.3/usage.mddocs/index-1.2.ymldocs/index-1.3.ymlfern/.gitignorefern/docs.ymlfern/fern.config.json
🚧 Files skipped from review as they are similar to previous changes (6)
- README.md
- docs/1.3/install-deb.md
- fern/.gitignore
- docs/1.2/install-deb.md
- docs/1.2/development.md
- docs/1.3/install-rpm.md
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 9
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/fern-docs-ci.yml:
- Around line 105-106: Validate the .version value with the existing preview
workflow’s semver validation before installation, assign it to VERSION, and
install the exact package using the VERSION variable. Apply this change at
.github/workflows/fern-docs-ci.yml lines 105-106 and
.github/workflows/publish-fern-docs.yml lines 54-55.
In `@docs/1.2/configuration.md`:
- Around line 196-201: Update the Kubernetes verification commands in
docs/1.2/configuration.md lines 196-201 and docs/1.3/configuration.md lines
203-206 to use helm get values --all, ensuring both examples display chart
defaults and user overrides.
- Around line 104-107: Pin the Helm chart version in both installation examples:
update docs/1.2/configuration.md lines 104-107 to use --version 1.2.1, and
docs/1.3/configuration.md lines 109-114 to use --version 1.3.0, preserving the
existing command structure.
In `@docs/1.2/install-helm.md`:
- Around line 172-178: Update the DCGM troubleshooting commands near the
DCGM_URL environment check to use the configured $DCGM_URL for connectivity
testing instead of the hardcoded nvidia-dcgm.gpu-operator.svc:5555 endpoint.
Make the kubectl service lookup explicitly default-only or otherwise
configurable, preserving the documented custom env.DCGM_URL override behavior.
In `@docs/1.2/install-rpm.md`:
- Around line 80-84: Update the release link and package version placeholders in
the installation and update sections to target the documented 1.2 release line:
link to the v1.2.1 release and require a compatible 1.2.x RPM instead of using
the latest release or unconstrained VERSION.
In `@docs/1.2/usage.md`:
- Around line 304-313: The “Exposing the Agent for External Monitoring”
documentation uses an unsafe all-interfaces listener as the primary example.
Make 127.0.0.1:15133 the default example, retain a specific remote address only
with guidance to restrict access through a firewall or private network, and
document that remote scraping should use a TLS-authenticated reverse proxy
because the TCP API is unauthenticated plaintext HTTP.
In `@docs/1.3/configuration.md`:
- Around line 63-65: Update the configuration documentation around the
duration-valued environment variable descriptions to state that the table covers
both Fleet Intelligence settings and process-level environment tuning. Remove
MALLOC_ARENA_MAX from the telemetry exporter and runtime interval description,
and describe its glibc allocator behavior separately.
In `@docs/1.3/development.md`:
- Around line 33-52: Update the project-structure code fence in the
documentation to include the `text` language identifier after the opening
backticks, preserving the diagram contents unchanged.
In `@docs/1.3/install-helm.md`:
- Around line 36-44: Update the enrollment Secret creation instructions under
“Create enrollment secret” to avoid passing ENROLL_TOKEN via the kubectl command
line. Use a safer input mechanism that does not expose the token in process
arguments, while preserving the existing secret name, namespace, and token key
behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: d4c79c0e-08d1-415f-88ee-2db8b2831965
📒 Files selected for processing (24)
.github/workflows/fern-docs-ci.yml.github/workflows/fern-docs-preview-build.yml.github/workflows/fern-docs-preview-comment.yml.github/workflows/publish-fern-docs.ymlREADME.mddocs/1.2/architecture.mddocs/1.2/configuration.mddocs/1.2/development.mddocs/1.2/install-deb.mddocs/1.2/install-helm.mddocs/1.2/install-rpm.mddocs/1.2/usage.mddocs/1.3/architecture.mddocs/1.3/configuration.mddocs/1.3/development.mddocs/1.3/install-deb.mddocs/1.3/install-helm.mddocs/1.3/install-rpm.mddocs/1.3/usage.mddocs/index-1.2.ymldocs/index-1.3.ymlfern/.gitignorefern/docs.ymlfern/fern.config.json
🚧 Files skipped from review as they are similar to previous changes (6)
- README.md
- docs/1.3/install-deb.md
- fern/.gitignore
- docs/1.2/install-deb.md
- docs/1.2/development.md
- docs/1.3/install-rpm.md
🛑 Comments failed to post (2)
docs/1.3/configuration.md (1)
63-65: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Separate allocator tuning from Fleet Intelligence settings.
MALLOC_ARENA_MAXcontrols glibc allocator behavior; it does not modify telemetry exporter configuration or runtime loop intervals. Clarify that this table includes process-level environment tuning in addition to Fleet Intelligence settings.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/1.3/configuration.md` around lines 63 - 65, Update the configuration documentation around the duration-valued environment variable descriptions to state that the table covers both Fleet Intelligence settings and process-level environment tuning. Remove MALLOC_ARENA_MAX from the telemetry exporter and runtime interval description, and describe its glibc allocator behavior separately.docs/1.3/install-helm.md (1)
36-44: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Avoid exposing the enrollment token through the kubectl command line.
--from-literal=token="$ENROLL_TOKEN"expands the secret into kubectl’s process arguments, allowing exposure through/proc/<pid>/cmdlineor process listings. This conflicts withdocs/1.3/usage.md’s recommendation to avoid command-line token exposure.Proposed fix
-kubectl create secret generic "$ENROLL_TOKEN_SECRET_NAME" \ - --namespace "$NS" \ - --from-literal=token="$ENROLL_TOKEN" +printf '%s' "$ENROLL_TOKEN" | + kubectl create secret generic "$ENROLL_TOKEN_SECRET_NAME" \ + --namespace "$NS" \ + --from-file=token=/dev/stdin📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.## Create enrollment secret If you need to enroll nodes, create the token Secret. The secret name should match the `ENROLL_TOKEN_SECRET_NAME` variable set above:🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/1.3/install-helm.md` around lines 36 - 44, Update the enrollment Secret creation instructions under “Create enrollment secret” to avoid passing ENROLL_TOKEN via the kubectl command line. Use a safer input mechanism that does not expose the token in process arguments, while preserving the existing secret name, namespace, and token key behavior.
|
Thanks for this PR! Maintaining separate directories such as docs/1.2 and docs/1.3 on main feels unintuitive and could allow release documentation to drift. Also, patch releases can differ—for example, 1.2.1 may have different behavior, configuration, or installation instructions from 1.2.0—so versioning only by major/minor may not be precise enough. I'm proposing this change:
This would give each released artifact an exact matching documentation snapshot without maintaining multiple copies on main. |
|
I will work on making the CI pull the latest two major versions into what Fern needs. We'll only keep 2 major versions since we don't support being further behind than that.. in fact right now we don't support being behind 1.3, based on the service requiring 1.3. We also shouldn't need different documents for minor version (ie. Z), if we need to change the documents for minor versions, it actually a major version release ... Z should only be patches, not functionality changes. |
2c2bcb0 to
af95192
Compare
…fleet-intel/agent - Restructure docs/ into versioned subdirectories (1.2/, 1.3/) sourced from the v1.2.1 and v1.3.1 release tags respectively, making the repo the single source of truth for agent documentation - Add fern/ scaffold (docs.yml, fern.config.json) targeting docs.nvidia.com/fleet-intel/agent with a 1.2/1.3 version selector; version management is manual per minor release, not per patch tag - Add docs/index-1.2.yml and docs/index-1.3.yml navigation files - Add GitHub Actions workflows for Fern CI (check + lychee link check), PR preview (build + comment), and publish on release - Fix MDX safety issues in both doc versions (bare angle brackets, autolink syntax) and replace cross-directory ../CONTRIBUTING.md link with a GitHub blob URL - Update README to direct users to docs.nvidia.com/fleet-intel/agent rather than the in-repo docs/ files Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@users.noreply.github.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
- Skip publish job for pre-release tags (e.g. v1.3.2-rc.1); only stable releases and manual workflow_dispatch trigger production publish - Explicitly fail the publish step when fern generate --docs does not emit a published URL, preventing silent success on output format changes Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Without -e, a fern generate failure would not terminate the step immediately — execution would continue to the URL grep and fail with a misleading error. -u catches unset variable references as an added guard. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Documentation is now maintained as a single flat docs/ tree (HEAD/main) rather than static per-version subdirectories. Versioned content is fetched from release tags at publish time by a new script, so adding a new release automatically updates the published site with no manual changes to fern/docs.yml needed. - Remove docs/1.2/, docs/1.3/, docs/index-1.2.yml, docs/index-1.3.yml; restore flat docs/*.md (content from v1.3.1, MDX fixes preserved) - fern/docs.yml: switch from versions: to navigation: pointing at HEAD docs, so fern check (PRs) and fern docs dev work without any generated files - Add fern/kept-versions.json to configure how many major.minor version groups to retain (default 2); increment to keep more - Add fern/versions/ to fern/.gitignore — version content and nav files are generated at publish time and never committed - Add scripts/docs-fetch-versions.py: discovers the latest patch tag per major.minor group, stages docs under fern/versions/<ver>-content/, applies MDX safety fixes, and generates per-version nav YML files. --list flag for dry-run inspection; --patch-fern-docs flag patches fern/docs.yml for a versioned local preview (restore with git checkout fern/docs.yml) - Rework publish-fern-docs.yml: runs the fetch script, patches fern/docs.yml in-runner with a versions: block from the manifest, then publishes and restores the original - fern-docs-preview-build.yml: remove frozen version checkout (no longer needed; PR previews show HEAD docs only via navigation:) - CONTRIBUTING.md: add Documentation section covering prerequisites, HEAD-only preview, versioned preview with --patch-fern-docs, and steps for adding or removing a doc page Signed-off-by: Ed Balduf <ebalduf@nvidia.com> Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
CI workflows: - Validate fern.config.json version against semver before npm install in fern-docs-ci.yml and publish-fern-docs.yml, matching the pattern already used in fern-docs-preview-comment.yml Docs (docs/ working tree): - usage.md: add missing `text` language tag on enrollment output code fence - usage.md: correct component name accelerator-nvidia-temperature → accelerator-nvidia-dcgm-thermal in metrics API example - development.md: fix `test` typo → `text` language tag on project structure diagram code fence - install-helm.md: replace --from-literal=token="$ENROLL_TOKEN" with printf pipe to --from-file=token=/dev/stdin to avoid token exposure in /proc/<pid>/cmdline - configuration.md: add note clarifying MALLOC_ARENA_MAX is a Linux process-level tuning parameter, not a Fleet Intelligence setting Signed-off-by: Ed Balduf <ebalduf@nvidia.com> Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Signed-off-by: "Ed Balduf" <ebalduf@nvidia.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
Signed-off-by: "Ed Balduf" <ebalduf@nvidia.com> Signed-off-by: Ed Balduf <ebalduf@nvidia.com>
ea9e535 to
b94c42d
Compare
…fleet-intel/agent
Description
This will move the docs into docs.nvidia.com/fleet-intel/agent for publishing, but leave the sources here in this repo. Contributors can continue to work with the docs here, but we'll cut specific releases for the docs.nvidia.com site when we make a major release (i.e. 1.2, 1.3 and 1.4). This will give us a more coheasive document set at docs.nvidia.com
Summary by CodeRabbit
New Features
Documentation
Automation / Release